This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
Re: Please explain the 8.5.3 64Gb logic size feature
The DAOS feature stores attachment data outside of the NSF file. That introduced the concept of 'logical' and 'physical' size of an NSF. The logical size of the NSF is the size of the NSF plus the size of all attachments stored in DAOS that are referenced by that NSF. The physical size of the NSF is the size of the NSF file on disk, as viewed with an OS-level file information command such as dir or ls, and does not include the size of any attachments stored in DAOS.
The physical size of the NSF must still remain under the 64Gb limit. Storing attachment data outside of the NSF means the logical size can exceed 64Gb while the physical size remains below the 64Gb limit.
Although there was nothing in any release of DAOS that prevented the logical size of the NSF exceeding 64Gb, there was no official support for it. The 8.5.3 release introduces support for logical NSF sizes in excess of 64Gb, and contains safeguards against problems introduced by moving NSF files out of DAOS once they have exceeded 64Gb logical size.
Feedback response number PMAO8NDJ9M created by ~Dan Zeklulygon on 11/07/2011